At 23:53 +0300 on 28/06/1999, JT Kirkpatrick wrote:
> ouch. hard to think of dollars only when you are paying vendors,
> technicians, billing customers, etc. surely i won't have to make an int
> field for the dollars and an int field for the cents!!! the money field
> would work nicely if the odbc driver would handle it correctly!
>
> i forwarded this to the odbc list -- any idea why a money field can't be
> used from msaccess97 through the odbc??
Perhaps as a work around you should use an integer field, which is scaled
two places to the left? That is, if you have 300.52 dollars, you keep the
number 30052 in the field. Surely you can play around with the forms you
use, so that the real field will be hidden, and get its value from a
visible field multiplied by 100.
It becomes a problem if your sums can go beyond the 2^31 limit. But if you
have 6.4, you may use int8 and double your upper limit.
The problem with the money type is that queries on it return it with a
currency mark, which I'm sure is bad for odbc.
Herouth
--
Herouth Maoz, Internet developer.
Open University of Israel - Telem project
http://telem.openu.ac.il/~herutma